(21/9)
Here is my part of the presentation, or at least an almost final draft. There is a Word document with speaking notes about the design process, and some slides. They don't exactly correlate yet though, so I will edit them once I've seen all the other parts. -Michael
(21/9)
This is a draft organisation diagram, which is partly a state transition diagram, and partly a list of functions and input-output modes. -Michael State_diagram_draft.jpg
Okay, *final* version: State_Transition.jpg
-Duncan
The system architecture is a very high level diagram about how the system is structured. In this case, it will primarily focus on what functions need to be written, and how they will connect to each other. A function shown here might ultimately be broken into smaller functions, but the purpose of this diagram is to define the key operations that need to be performed by the program. If you want to edit this picture, use this word document: sysarch.doc.
Notes
The above diagram is just intended as a very high level overview - there are some things that have been omitted.
The 'Operation Mode' block is quite complex and probably requires some further explaining. Essentially, there are many functions that the scales need to be able to perform, and each of the blocks contained within the 'Operation Mode' block represent a single task (there may be some missing). When the user executes a task, the function may make several weighings or several outputs to various output modules, etc - the details of which are a little too complicated for this diagram. One of the first things that needs to be done is to draft up how each of these operations will execute so that we can detail how the inputs and outputs need to function.
System Architecture
User interface - software part
(21/9)Here is my part of the presentation, or at least an almost final draft. There is a Word document with speaking notes about the design process, and some slides. They don't exactly correlate yet though, so I will edit them once I've seen all the other parts. -Michael
Draft state transition diagram
(21/9)This is a draft organisation diagram, which is partly a state transition diagram, and partly a list of functions and input-output modes. -Michael
State_diagram_draft.jpg
Okay, *final* version:
State_Transition.jpg
-Duncan
The system architecture is a very high level diagram about how the system is structured. In this case, it will primarily focus on what functions need to be written, and how they will connect to each other. A function shown here might ultimately be broken into smaller functions, but the purpose of this diagram is to define the key operations that need to be performed by the program. If you want to edit this picture, use this word document: sysarch.doc.
Notes
The above diagram is just intended as a very high level overview - there are some things that have been omitted.The 'Operation Mode' block is quite complex and probably requires some further explaining. Essentially, there are many functions that the scales need to be able to perform, and each of the blocks contained within the 'Operation Mode' block represent a single task (there may be some missing). When the user executes a task, the function may make several weighings or several outputs to various output modules, etc - the details of which are a little too complicated for this diagram. One of the first things that needs to be done is to draft up how each of these operations will execute so that we can detail how the inputs and outputs need to function.